Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

0140

reference: 185-tree-1
name: 0140
tree-preservation-order: undefined
185-tpo-1
uprn
address-text
point: POINT (-0.937787 50.864532)
geometry: MULTIPOLYGON (((-0.937702 50.864523,-0.937706 50.864540,-0.937718 50.864555,-0.937737 50.864567,-0.937760 50.864575,-0.937786 50.864578,-0.937813 50.864576,-0.937837 50.864568,-0.937856 50.864556,-0.937868 50.864541,-0.937873 50.864525,-0.937869 50.864508,-0.937857 50.864493,-0.937839 50.864481,-0.937815 50.864473,-0.937789 50.864470,-0.937763 50.864472,-0.937739 50.864480,-0.937719 50.864492,-0.937707 50.864507,-0.937702 50.864523)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL